AV data recording apparatus and method, and disk recorded by the same

ABSTRACT

An AV data recording apparatus and an AV data recording method are provided, in which even in the case of using the UDF file system, seeking can be minimized. The AV data recording method has file management information for managing continuous blocks on a disk as an extent, and dividing the extent into groups so as to manage the extent as a file, wherein a new directory is created on a disk, and a not recorded but allocated extent is kept as a reservation region for recording file management information.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to an AV data recording apparatus andmethod, suitable for recording/reproducing AV (audio-video) data such asa digital image.

2. Description of the Related Art

In recent years, optical disks are being used as recording media forrecording digital images including animation, due to their increaseddensity. Optical disks are applied in a wide range; specifically, theyare applied to peripheral equipment of computers, video players for useat home, etc. Furthermore, it is expected that optical disks will beused as recording media, in place of tape media in the future.

In order to handle data for common use in such a wide range ofapplications, data generally is managed as a logical unit (i.e., file).As an example of such a file management method, there is a file systemusing a format based on the UDF (Universal Disk Format) standard.

The UDF standard is prescribed so as to ensure medium compatibilityamong various kinds of computer OSes (Operating Systems). The UDFstandard also is used in consumer equipment such as DVD-Video players.Furthermore, it is expected that the UDF standard will be supported overa wider platform in the future.

Hereinafter, the structure of a file system (hereinafter, referred to asa “UDF file system”) using the UDF standard will be described withreference to the drawings. FIG. 35 shows an example of a structure of anapparatus for recording/reproducing data adopting a conventional AV datarecording method.

In FIG. 35, reference numeral 101 denotes a disk (e.g., amagneto-optical disk), and 102 denotes a recording medium drivingsection. When the disk 101 is, for example, a magneto-optical disk, therecording medium driving section 102 may be composed of a spindle motor,or the like.

Reference numeral 103 denotes a recording/reproducing section, which iscomposed of an optical pickup, a magnetic head, a servo circuit, amodulation/demodulation circuit, and the like, when the disk 101 is, forexample, a magneto-optical disk. Reference numeral 104 denotes a memorysection, which stores data temporarily during recording/reproduction.Reference numeral 105 denotes a disk drive unit, which is composed ofthe disk 101, the recording medium driving section 102, therecording/reproducing section 103, and the memory section 104.

Reference numeral 106 denotes an AV signal processing section, whichsubjects an AV input signal (that is input through a CCD camera, forexample) to processing such as MPEG compression or subjects AV data readfrom the disk 101 to processing such as MPEG decoding, and outputs theresults to a monitor or the like.

Furthermore, reference numeral 107 denotes a system control section,which controls the AV signal processing section 106 and the disk driveunit 105.

When data is recorded in an apparatus for recording/reproducing datathus constructed, an AV signal input to the AV signal processing section106 is subjected to image compression in accordance with the MPEG systemor the like, and transferred to the memory section 104 under the controlof the system control section 107.

Next, the system control section 107 operates the recording mediumdriving section 102 and the recording/reproducing section 103 to recorddata in the memory section 104 onto the disk 101.

For reproduction of data, the system control section 107 operates therecording medium driving section 102 and the recording/reproducingsection 103 to transfer data recorded on the disk 101 to the memorysection 104.

Then, the data in the memory section 104 is read under the control ofthe system control section 107, and is output from the AV signalprocessing section 106 as an AV signal.

Next, an example of a structure of the UDF file system that is aconventional file management method will be described with reference tothe drawings. FIG. 36 shows the structure in a volume space of the UDFformed on the disk 101.

In FIG. 36, in order to handle the disk 101 as a logical volume, thedisk 101 is divided into units called sectors, and the sectors areassigned logical sector numbers (LSNs) from 0 (Zero) to a last logicalnumber (Last LSN). In a leading portion and a trailing portion of thevolume space, a volume structure is recorded, respectively. Furthermore,a partition space is allocated between the volume structures. In thepartition space, file structure information and a file (i.e., user data)are recorded.

In the partition space, logical block numbers (LBNs) are allocated in arange of 0 (Zero) to a last logical block number (Last LBN) from aleading sector on a sector basis. FIG. 37 shows a structure of thepartition space when a directory structure shown in FIG. 38 is recordedon the disk 101.

As shown in FIG. 38, a directory Dir1 is present under a root directory,and File1_1 and File1_2 are present under the directory Dir1. In thiscase, in FIG. 37, a space bitmap descriptor is recorded in LBN=0 to 79.

The space bitmap descriptor has a space bitmap showing whether or noteach logical block is allocatable. Each bit of the space bitmapcorresponds to a respective logical block. When a bit value is “1”, itscorresponding logical block is unallocated, and when a bit value is “0”,its corresponding logical block is allocated.

In LBN=80, a file set descriptor is recorded. In the file setdescriptor, positional information of a file entry of the root directoryis recorded. The file entry will be described in detail later.

In LBN=81, a terminating descriptor is recorded. The terminatingdescriptor represents an end of a file set descriptor string.

In LBN=82, a file entry of the root directory is recorded. The fileentry is used for storing various pieces of attribute informationspecific to each file, information on the recorded position and size ofeach file, and the like, and managing each file as a group of extents.The extent will be described in detail later.

FIG. 39 shows a structure of the file entry. In a descriptor tag field,information is recorded for identifying various kinds of descriptorssuch as a space bitmap descriptor, a file set descriptor, and a fileentry in the partition space. In the case of the file entry, “261” isdescribed. In an ICB (Information Control Block) tag field, attributeinformation on the file entry itself is recorded. An extended attributefield is used for describing attribute information other than thatprescribed in an attribute information field in the file entry. In anallocation descriptor field, the required number of allocationdescriptors are recorded for managing a region of continuous logicalblocks as one extent.

FIG. 40 shows a structure of the allocation descriptor. In theallocation descriptor, an extent is represented by an extent length andan extent position.

FIG. 41 shows interpretation of the 2 most significant bits of theextent length included in the allocation descriptor. An allocated stateand a recorded state of the extent are represented by the value of the 2most significant bits. The value “0” represents an extent recorded andallocated, and file data is recorded therein. The value “1” representsan extent not recorded but allocated, and its region is allocated to aparticular file/directory; however, no data is recorded therein. Thevalue “2” represents an extent not recorded and not allocated, and nodata is recorded therein. The value “3” represents the extent that isthe next extent of the allocation descriptors. In the allocationdescriptor field of the file entry, a plurality of allocationdescriptors can be recorded, and collection of extents managed by theseallocation descriptors form one file. The extents forming a file arecalled a main data stream, in which user data is stored.

In a directory, a name of a file included in the directory, andpositional information on a file entry thereof are recorded. In the UDF,a directory also is a kind of a file. Referring to FIG. 37, directoriesare recorded in LBN=83 and LBN=85.

FIG. 42 shows an example of a structure of a directory file recorded inLBN=85. The directory file is composed of a plurality of file identifierdescriptors, and each file identifier descriptor has information on eachfile included in the directory. The main information associated witheach file identifier descriptor includes a name of a file to which thefile identifier descriptor corresponds and positional information on afile entry thereof. FIG. 43 shows an example of the logical structure ofa directory/file in file management information in accordance with theUDF standard.

In FIG. 43, the file set descriptor is recorded at a predeterminedposition in the partition space as a part of file managementinformation. In the file set descriptor, a recorded position of the fileentry of the root directory file is stored. In the file identifierdescriptor of the root directory file, a recorded position of the fileentry of the directory Dir1 is stored. In a file under the directoryDir1, a plurality of file identifier descriptors are present, and filenames and recorded positions of file entries of FILE1_1 and FILE1_2 arestored, respectively.

Furthermore, according to the UDF, an extended file entry can be used inplace of the above-mentioned file entry. FIG. 44 shows an example of astructure of an extended file entry. In the UDF standard, in adescriptor tag field of the extended file entry, “266” is described.

The extended file entry is different from the file entry, in that theextended file entry has a stream directory ICB field. In the streamdirectory ICB, positional information on a file entry for describing aspecial directory called a stream directory is stored.

FIG. 45 shows an example of a structure of the stream directory. Thestream directory also is a kind of a directory file, and is composed ofa plurality of file identifier descriptors in the same way as in ageneral directory file.

The stream directory file is different from a general directory file, inthat a file identifier descriptor in the stream directory is related toa special file called a named data stream.

Furthermore, in the stream directory, a main data stream is referred toas a parent entry, in place of a parent directory.

In the case of the named data stream, the collection of extents managedby allocation descriptors in an extended file entry also forms one datastream.

Accordingly, a file managed by an extended file entry is composed of onemain data stream, or one main data stream and at least one named datastream.

FIG. 46 shows an example of a directory/file logical structure when anextended file entry is used in accordance with the UDF standard. In FIG.46, the relationship among a file set descriptor, a root directory, adirectory Dir1, and files FILE1_1 and FILE_2 is the same as that shownin FIG. 43, except that an extended file entry is used in place of afile entry.

Referring to FIG. 44, in the stream directory ICB field of the extendedfile entry, a recorded position of a file entry in the stream directoryis stored.

In a file under the stream directory, a plurality of file identifierdescriptors are present, and names and recorded positions of extendedfile entries of named_stream_1 and named_stream_2 are stored in therespective file identifier descriptors.

Referring to FIG. 46, in the directory Dir1, three data streams: adirectory file (main data stream), and named_stream_1 and named_stream_2(named data streams) form one file.

Hereinafter, an operation of an apparatus for recording/reproducing datawill be described, in which a desired file is read from a disk having astructure in accordance with the above-mentioned UDF file system.

An operation of obtaining a recorded position of an intended file in ahierarchical structure as shown in FIG. 43 will be described. It isassumed that a file FILE1_1 is the intended one.

First, the content of a root directory file is read. More specifically,a position of a file entry of the root directory is obtained byreferring to a file set descriptor. Then, an allocation descriptor isread from the file entry to obtain the position and length of an extentof the root directory file, and data of the root directory file areread. By scanning information on the root directory file thus obtained,a file identifier descriptor matched with an intended directory nameDir1 can be detected.

Then, the content of the intended directory file is read. Morespecifically, when a file identifier descriptor matched with an intendeddirectory is detected, positional information of a file entry isobtained from the content of the file identifier descriptor, and thefile entry is read. An allocation descriptor is read from the file entryregarding the intended directory to obtain the position and length of anextent recorded in the allocation descriptor, and data of the directoryfile are read.

Finally, in order to read an intended file, data in a file under thedirectory Dir1 are scanned to detect a file identifier descriptormatched with an intended file name FILE1_1. When a file identifierdescriptor matched with the intended file name is detected, positionalinformation of a file entry is obtained from the file identifierdescriptor, and a file entry thereof is read. An allocation descriptoris read from the file entry to obtain the position and length of anextent recorded in the allocation descriptor, and data of the intendedfile FILE1_1 is read.

Next, an operation of an apparatus for recording/reproducing data willbe described, in which data are recorded on a disk having a structurebased on the UDF file system. Herein, the case will be described whereFILE1_3 is further recorded in the directory Dir1 with respect to a diskhaving the partition space shown in FIG. 37.

First, a space bitmap is scanned, and an unallocated logical block witha bit “1” is obtained. Data of FILE1_3 is recorded as an extent in theunallocated logical block. When recording of the extent is completed, afile entry indicating FILE1_3 is recorded in the unallocated logicalblock.

At this time, positional information on the extent indicating FILE1_3and the extent length are recorded in the file entry as a requirednumber of allocation descriptors. A file identifier descriptorindicating FILE1_3 is recorded in a file of a directory Dir1 that is aparent directory of FILE1_3.

In the file identifier descriptor, a file name of FILE1_3 and positionalinformation of the file entry thereof are recorded. A bit in the spacebitmap corresponding to a sector that has been allocated by the aboveprocessing is set at “0” so as to be in an allocated state.

FIG. 47 shows a logical volume space obtained as a result of the aboveprocessing. The order of processing with respect to file managementinformation is not particularly limited to the above example. Theprocessing may be performed in a different order.

Hereinafter, an operation of an apparatus for recording/reproducingapparatus will be described in which a desired named data stream is readfrom a disk having a structure based on the UDF file system. Herein, anoperation of obtaining a recorded position of an intended named datastream in a hierarchical structure as shown in FIG. 46 will bedescribed. In FIG. 46, it is assumed that named_stream_1 is the intendeddata stream.

An operation of reading a file entry of a directory Dir1 that is aparent directory of the named data stream named_stream_1 is as describedabove.

A stream directory ICB is read from an extended file entry of thedirectory Dir1, and an extended file entry of a stream directoryrecorded therein is obtained.

Then, an allocation descriptor is read from the extended file entry toobtain the position and length of an extent of the stream directory, anddata of the stream directory file is read.

Information on the obtained stream directory is scanned, whereby a fileidentifier descriptor matched with the name of the intended named datastream (i.e., named_stream_1) can be detected.

Positional information of an extended file entry is obtained from thecontent of the file identifier descriptor, and the extended file entryis read.

An allocation descriptor is read from the extended file entry regardingthe named data stream to obtain the position and length of an extentrecorded therein, and data of an intended named data stream(named_stream_1) is read.

A named data stream also is recorded in the same way as in a file,except that a file identifier descriptor for storing a recorded positionof an extended file entry of the named data stream is recorded in astream directory file.

The order of processing with respect to the named data stream is notparticularly limited to the above example, and the processing may beperformed in a different order.

However, the above-mentioned file management method using the UDF hasthe following problem. More specifically, according to the UDF, adirectory is recorded as a file in a partition space, and a file entryalso is recorded in the partition space. Therefore, the directory fileand the file entry may be distributed on a disk. Thus, in the case whereit is attempted to read all the files under a certain directory, when adirectory file and a file entry are distributed, seeking occurs oftenwith respect to a disk.

For example, referring to FIG. 47, file entries of FILE1_1, FILE1_2, andFILE1_3 are distributed; therefore, seeking cannot be avoided forreading them. When a file to be reproduced is the one which requiresreal time reproduction, such as an AV file, reproduction of the file maybe difficult due to the occurrence of seeking.

Similarly, in the case where real time recording is required as in an AVfile and the like, when a file entry is recorded after AV data isrecorded, seeking occurs with respect to a disk, and recording of AVdata during this time stops. This also applies to the case where a largeamount of still image files and the like subjected to JPEG compressionare recorded and browsed through.

It is conceivable to reduce seeking with respect to a disk by readingall the file management information to a memory and performing on-memoryprocessing, upon activation of an apparatus. Even in this case, seekingoccurs a number times, which prolongs an activation time. Furthermore, arequired memory capacity cannot be expected previously; therefore, it isdifficult to construct a system in which a calculator resource isdisposed efficiently.

SUMMARY OF THE INVENTION

Therefore, with the foregoing in mind, it is an object of the presentinvention to provide an AV data recording apparatus and method capableof minimizing seeking even in the case of using the UDF file system.

In order to achieve the above-mentioned object, the AV data recordingapparatus of the present invention, includes: a disk as a recordingmedium for AV data; a recording medium driving section for driving thedisk; a recording/reproducing section for recording data onto thedisk/reproducing the data from the disk; a memory section for storingdata temporarily; an AV signal processing section for performingconversion between an AV signal and a digital signal; and a systemcontrol section for controlling a recording method, wherein theapparatus has file management information for managing continuous blockson the disk as an extent, and dividing the extent into groups so as tomanage the extent as a file in the system control section, and a newdirectory is created on the disk, and the extent that has been allocatedis kept as a reservation region for recording the file managementinformation.

Because of the above-mentioned structure, even in the case of using theUDF, file management information of a file to be recorded is notdistributed on a disk, and seeking with respect to a disk can beminimized. Therefore, recording can be performed with high reliabilityat a high speed. Furthermore, by allocating a reservation region, otherinformation can be prevented from being recorded therein.

Furthermore, it is preferable that the reservation region is a part of amain data stream.

Furthermore, it is preferable that the reservation region is a part of anamed data stream.

Furthermore, it is preferable that, when the file is recorded on thedisk, attribute information of the file is recorded in the reservationregion.

Furthermore, it is preferable that the file is a transport stream ofMPEG, and the attribute information of the file recorded in thereservation region is a private stream containing a time map table of atransport stream. In this case, special reproduction such asfast-forward reproduction and fast-backward reproduction, reproductionat a specified time, and the like can be performed easily.

Furthermore, it is preferable that the file is an Exif image file, andthe attribute information of the file recorded in the reservation regionis additional information of the Exif image file. Since thumbnailinformation and the like are contained in the additional information,thumbnail information and the like can be reproduced at a high speed byreading only the additional information.

Furthermore, it is preferable that the reservation region is kept byrecording the file management information of the file previously. Inthis case, it is not required to scan a non-recorded region duringrecording of a file, so that seeking can be reduced.

Furthermore, it is preferable that, when a new subdirectory is createdunder the directory, an allocated extent is kept as a reservation regionfor recording the file management information of the file in thesubdirectory. In this case, the same effect can be expected even when anAV file is recorded in the subdirectory.

Furthermore, it is preferable that, when a new subdirectory is createdunder the directory, a directory file of the subdirectory is recorded inthe reservation region. This is because seeking can be reduced even inthe case of recording an AV file in the subdirectory.

Furthermore, it is preferable that, when the directory is created, adefective block in the reservation region is detected, and the defectiveblock is skipped. In this case, the continuity of data to be recorded inthe reservation region is not impaired, so that recording can beperformed with high reliability.

Furthermore, it is preferable that, in a case where the file is recordedon the disk, when a capacity of the reservation region becomesinsufficient, another reservation region different from the firstreservation region is kept in a continuous region on the disk to recordthe file. In this case, by minimizing seeking, recording/reproduction ofAV data can be prevented from being suspended.

Furthermore, it is preferable that, in a case where a thumbnail filecontaining a thumbnail image of the file is recorded on the disk, thethumbnail file is recorded in the reservation region. In this case,since seeking does not occur, even a thumbnail image with a largecapacity containing a plurality of pieces of image data can be displayedat a high speed.

In order to achieve the above-mentioned object, the AV data recordingmethod has file management information for managing continuous blocks ona disk as an extent, and dividing the extent into groups so as to managethe extent as a file, wherein a new directory is created on the disk,and the extent that has been allocated is kept as a reservation regionfor recording the file management information.

Because of the above-mentioned structure, even in the case of using theUDF, file management information of a file to be recorded is notdistributed in a disk, and seeking with respect to a disk can beminimized. As a result, recording can be performed with high reliabilityat a high speed. Furthermore, by allocating the reservation region,other information can be prevented from being recorded.

Furthermore, it is preferable that the reservation region is a part of amain data stream.

Furthermore, it is preferable that the reservation region is a part of anamed data stream.

Furthermore, it is preferable that, when the file is recorded onto thedisk, attribute information of the file is recorded in the reservationregion.

Furthermore, it is preferable that the file is a transport stream ofMPEG, and the attribute information of the file recorded in thereservation region is a private stream containing a time map table of atransport stream. In this case, special reproduction such asfast-forward reproduction and fast-backward reproduction, reproductionat a specified time, and the like can be performed easily.

Furthermore, it is preferable that the file is an Exif image file, andthe attribute information of the file recorded in the reservation regionis additional information of the Exif image file. Since thumbnailinformation and the like are contained in the additional information,thumbnail information and the like can be reproduced at a high speed byreading only the additional information.

Furthermore, it is preferable that the reservation region is kept byrecording the file management information of the file previously. Inthis case, it is not required to scan a non-recorded region duringrecording of a file, so that seeking can be reduced.

Furthermore, it is preferable that, when a new subdirectory is createdunder the directory, an allocated extent is kept as a reservation regionfor recording file management information of the file in thesubdirectory. In this case, the same effect can be expected even when anAV file is recorded in the subdirectory.

Furthermore, it is preferable that, when a new subdirectory is createdunder the directory, a directory file of the subdirectory is recorded inthe reservation region. This is because seeking can be reduced even inthe case of recording an AV file in the subdirectory.

Furthermore, it is preferable that, when the directory is created, adefective block in the reservation region is detected, and the defectiveblock is skipped. In this case, the continuity of data to be recorded inthe reservation region is not impaired, so that recording can beperformed with high reliability.

Furthermore, in a case where the file is recorded onto the disk, when acapacity of the reservation region becomes insufficient, anotherreservation region different from the reservation region is kept in acontinuous region on the disk to record the file. In this case, byminimizing seeking, recording/reproduction of AV data can be preventedfrom being suspended.

Furthermore, it is preferable that, in a case where a thumbnail filecontaining a thumbnail image of the file is recorded onto the disk, thethumbnail file is recorded in the reservation region. In this case,since seeking does not occur, even thumbnail image with a large capacitycontaining a plurality of pieces of image data can be displayed at ahigh speed.

These and other advantages of the present invention will become apparentto those skilled in the art upon reading and understanding the followingdetailed description with reference to the accompanying figures.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a structure of an AV data recording apparatus in Embodiment1 of the present invention.

FIG. 2 illustrates an initial directory structure in the AV datarecording apparatus in Embodiment 1 of the present invention.

FIG. 3 illustrates an initial partition space in the AV data recordingapparatus in Embodiment 1 of the present invention.

FIG. 4 is a flow chart showing recording processing of an AV file in theAV data recording apparatus in Embodiment 1 of the present invention.

FIG. 5 illustrates a partition space after an AV file is recorded in theAV data recording apparatus in Embodiment 1 of the present invention.

FIG. 6 illustrates an initial directory structure in the AV datarecording apparatus in Embodiment 2 of the present invention.

FIG. 7 illustrates an initial partition space in the AV data recordingapparatus in Embodiment 2 of the present invention.

FIG. 8 illustrates an initial directory structure in the AV datarecording apparatus in Embodiment 3 of the present invention.

FIG. 9 illustrates an initial partition space in the AV data recordingapparatus in Embodiment 3 of the present invention.

FIG. 10 illustrates an AV file structure in the AV data recordingapparatus in Embodiment 4 of the present invention.

FIG. 11 illustrates a time map in the AV data recording apparatus inEmbodiment 4 of the present invention.

FIG. 12 illustrates a time map in the AV data recording apparatus inEmbodiment 4 of the present invention.

FIG. 13 illustrates a time map in the AV data recording apparatus inEmbodiment 4 of the present invention.

FIG. 14 illustrates an initial partition space in the AV data recordingapparatus in Embodiment 4 of the present invention.

FIG. 15 is a flow chart showing recording processing of an AV file inthe AV data recording apparatus in Embodiment 4 of the presentinvention.

FIG. 16 illustrates a partition space after an AV file is recorded inthe AV data recording apparatus in Embodiment 4 of the present invention

FIG. 17 illustrates a date structure of a still image file in an AV datarecording apparatus in Embodiment 5 of the present invention.

FIG. 18 illustrates a date structure of a still image file in the AVdata recording apparatus in Embodiment 5 of the present invention.

FIG. 19 illustrates a multi-directory structure in the AV data recordingapparatus in Embodiment 5 of the present invention.

FIG. 20 illustrates an initial directory structure in the AV datarecording apparatus in Embodiment 6 of the present invention.

FIG. 21 illustrates an initial partition space in the AV data recordingapparatus in Embodiment 6 of the present invention.

FIG. 22 is a flow chart showing recording processing of an AV file inthe AV data recording apparatus in Embodiment 6 of the presentinvention.

FIG. 23 illustrates a directory structure after a subdirectory iscreated in the AV data recording apparatus in Embodiment 6 of thepresent invention.

FIG. 24 illustrates a partition space after a subdirectory is created inthe AV data recording apparatus in Embodiment 6 of the presentinvention.

FIG. 25 is a flow chart showing recording processing of an AV file inthe AV data recording apparatus in Embodiment 6 of the presentinvention.

FIG. 26 illustrates a partition space after an AV file is recorded inthe AV data recording apparatus in Embodiment 6 of the presentinvention.

FIG. 27 is a flow chart showing processing of creating a subdirectory inan AV data recording apparatus in Embodiment 7 of the present invention.

FIG. 28 illustrates a partition space after a subdirectory is created inthe AV data recording apparatus in Embodiment 7 of the presentinvention.

FIG. 29 is a flow chart showing processing of recording AV data under asubdirectory in the AV data recording apparatus in Embodiment 7 of thepresent invention.

FIG. 30 illustrates a partition space after an AV file is recorded in asubdirectory in the AV data recording apparatus in Embodiment 7 of thepresent invention.

FIG. 31 illustrates a directory structure after a subdirectory iscreated in the AV data recording apparatus in Embodiment 7 of thepresent invention.

FIG. 32 illustrates a partition space before a new AV reservation regionis kept in an AV data recording apparatus in Embodiment 10 of thepresent invention.

FIG. 33 is a flow chart showing processing of recording an AV file inthe AV data recording apparatus in Embodiment 10 of the presentinvention.

FIG. 34 illustrates a partition space after a new AV reservation regionis kept in the AV data recording apparatus in Embodiment 10 of thepresent invention.

FIG. 35 shows a structure of a conventional AV data recording apparatus.

FIG. 36 illustrates a volume space structure in the conventional AV datarecording apparatus.

FIG. 37 illustrates a partition space in the conventional AV datarecording apparatus.

FIG. 38 illustrates a directory structure in the conventional AV datarecording apparatus.

FIG. 39 illustrates a file entry in the conventional AV data recordingapparatus.

FIG. 40 illustrates an allocation descriptor in the conventional AV datarecording apparatus.

FIG. 41 illustrates interpretation of an extent length in theconventional AV data recording apparatus.

FIG. 42 illustrates a structure of a directory file in the conventionalAV data recording apparatus.

FIG. 43 illustrates a hierarchical structure of a file in theconventional AV data recording apparatus.

FIG. 44 illustrates an extended file entry in the conventional AV datarecording apparatus.

FIG. 45 illustrates a structure of a stream directory file in theconventional AV data recording apparatus.

FIG. 46 illustrates a hierarchical structure of a named data stream inthe conventional AV data recording apparatus.

FIG. 47 illustrates a partition space after recorded in the conventionalAV data recording apparatus.

DESCRIPTION OF THE PREFERRED EMBODIMENTS

Hereinafter, embodiments of an AV data recording apparatus of thepresent invention will be described with reference to the drawings. Inthe following description, a file containing voice data and video dataencoded in accordance with the MPEG system, the JPEG system, or the likewill be referred to as an “AV file”. In the present specification, diskscollectively refer to recording media having a disk shape, such as anoptical disk, a hard disk, and the like (e.g., DVD-RAM, MO, DVD-R,DVD−RW, DVD+RW, etc.).

Embodiment 1

FIG. 1 shows the structure of an AV data recording apparatus inEmbodiment 1 of the present invention. In FIG. 1, reference numeral 1denotes a disk (e.g., a magneto-optical disk), and 2 denotes a recordingmedium driving section, which may be composed of a spindle motor, or thelike, when the disk 1 is, for example, a magneto-optical disk.

Reference numeral 3 denotes a recording/reproducing section. When thedisk 1 is, for example, a magneto-optical disk, therecording/reproducing section 3 is composed of an optical pickup, amagnetic head, a servo circuit, a modulation/demodulation circuit, andthe like. Reference numeral 4 denotes a memory section, whichtemporarily stores data during recording/reproduction. Reference numeral5 denotes a disk drive unit, which is composed of the disk 1, therecording medium driving section 2, the recording/reproducing section 3and the memory section 4.

Reference numeral 6 denotes an AV signal processing section, whichsubjects an AV input signal (that is input from a CCD camera, forexample) to processing such as MPEG compression or subjects AV data readfrom the disk medium to processing such as MPEG decoding, and outputsthe results to a monitor or the like. Reference numeral 7 denotes asystem control section, which controls the AV signal processing section6 and the disk drive unit 5.

When data is recorded in an AV data recording apparatus thusconstructed, an AV signal input to the AV signal processing section 6 issubjected to image compression processing based on the MPEG system, andtransferred to the memory section 4 under the control of the systemcontrol section 7. Next, the system control section 7 operates therecording medium driving section 2 and the recording/reproducing section3 to record data in the memory section 4 onto the disk 1.

When data is reproduced, the system control section 7 operates therecording medium driving section 2 and the recording/reproducing section3 to transfer data recorded on the disk 1 to the memory section 4. Then,the data in the memory section 4 is read under the control of the systemcontrol section 7, and is output from the AV signal processing section 6as an AV signal.

FIG. 2 illustrates a file/directory structure immediately after adirectory for recording an AV file is created in Embodiment 1 of thepresent invention. In FIG. 2, Root surrounded by an ellipse represents aroot directory, and AV_DIR1 represents a directory for recording an AVfile, respectively.

FIG. 3 illustrates a data structure in a partition space in which thedirectory structure shown in FIG. 2 is recorded on a disk used in the AVdata recording apparatus in Embodiment 1 of the present invention. InFIG. 3, in LBN=0 to 79, a space bitmap descriptor is recorded. LBN=251to Last is “unallocated”. Therefore, bits corresponding to the sectorstherein are set at “1”.

Furthermore, in LBN=80, a file set descriptor is recorded. When a fileentry is that of the root directory, positional information thereof isrecorded in the file set descriptor. Furthermore, in LBN=81, aterminating descriptor is recorded.

Furthermore, a file entry of the root directory, a directory file of theroot directory, and a file entry of the directory AV_DIR1 are recordedin LBN=82, LBN=83, and LBN=84, respectively.

LBN=85 is an extent (1) in which a directory file of the directoryA_DIR1 is recorded. Similarly, LBN=86 to 250 is an extent (2) of thedirectory AV_DIR1. The value of the 2 most significant bits of anallocation descriptor is determined so that the extent (2) is “notrecorded” but “allocated”. Thus, in an operation of a conventional filesystem, data cannot be written in LBN=86 to 250. Hereinafter, the extent(2) will be referred to as an “AV reservation region”. Since LBN=0 to250 is “allocated” as described above, corresponding bits in the spacebitmap are set at “0” (Zero).

In Embodiment 1, the capacity of the “not recorded” but “allocated”extent in the directory AV_DIR1 in an initial state of the recordingmedium is previously determined. Because of this, inrecording/reproduction with respect to the disk 1 as shown in FIG. 4(Step S401), a system structure is obtained in which the content ofLBN=0 to 250 on the disk 1 is read to the memory section 4, and seekingduring recording/reproduction can be reduced.

FIG. 4 is a flow chart showing the process of recording an AV file ontoa disk having the above-mentioned data structure. When an AV file startsbeing recorded in accordance with a user's instruction or the like, thecontent of LBN=0 to 250 on the disk 1 is read to the memory section 4(Step S401). Then, information in the AV reservation region in thememory section 4 is scanned to determine whether or not there is anon-recorded region sufficient for newly recording a file identifierdescriptor and a file entry (Step S402). If it is determined that thereis not a sufficient non-recorded region (Step S402: No), errorprocessing is performed, and recording of an AV file is ended. If it isdetermined that there is a sufficient non-recorded region, a fileidentifier descriptor and a file entry are recorded in a non-recordedregion in the AV reservation region in the memory section 4 (Step S403).

At this time, the size of the extent of the directory AV_DIR1 is changeddue to recording of the file identifier descriptor and the file entry,so that an allocation descriptor of the file entry of the directoryAV_DIR1 is rewritten in accordance with the change. More specifically,the extent length of the extent (1) is changed by addition of the fileidentifier descriptor, and a portion in which the file entry has beenrecorded is excluded from the extent (2).

Next, the space bitmap in the memory section 4 is scanned to determinewhether or not there are the required number of unallocated logicalblocks for recording an AV file (Step S404). If it is determined thatthere are no required number of unallocated logical blocks (Step S404:No), error processing is performed, and recording of an AV file isended. When it is determined that there are the required number ofunallocated logical blocks, data are recorded in logical blocks on therecording medium corresponding to the unallocated region obtained inStep S404 (Step S405).

When recording of AV file data is completed, in order to update the filemanagement information of an AV file, information on the position andlength of the extent of the AV file is recorded in an allocationdescriptor in the file entry in the memory section 4 created in Step 403(Step S406). Furthermore, required information such as a file name and afile creation time also are updated with respect to the file identifierdescriptor and the file entry, in addition to the allocation descriptor.

Next, with respect to the space bitmap in the memory section 4, bitscorresponding to the logical blocks in which data has been recorded inStep 405 are changed to “1” representing an “allocated” state (StepS407). Then, the content of the memory section 4 is written back toLBN=0 to 250 on the disk 1 (Step S408). Thus, an AV file is recorded inthe directory AV_DIR1.

In the case of recording a plurality of AV files continuously, in theflow chart in FIG. 4, Steps S402 to S407 are repeated after Step S401until recording of all the AV files is completed, and after recording ofall the AV files is completed, a process should proceed to Step S408.

Because of this, it is not required to write a file identifierdescriptor and a file entry onto a recording medium every time a file iscreated, and seeking can be reduced substantially.

FIG. 5 shows a data structure in the partition space after FILE1. DATand FILE2. DAT that are AV files are recorded in the directory AV_DIR1in accordance with the flow chart shown in FIG. 4. Herein, in the AVreservation region, logical blocks are used for recording new fileentries in the decreasing order of LBN. On the other hand, a fileidentifier descriptor is added to the end of the extent (1) that is arecorded extent of the directory AV_DIR1. Since the file identifierdescriptor and the file entry both have a data structure with a variablelength, it is desirable that the file identifier descriptor is recordedin the increasing order of LBN in the AV reservation region, and thefile entry is recorded in the decreasing order of LBN.

In the case where there is an insufficient capacity in the extent (1)for describing a file identifier descriptor as a result of addition of afile, the allocation descriptor in the directory AV_DIR1 is corrected sothat a block adjacent to the extent (1) in the AV reservation region isincluded in the extent (1), and a file identifier descriptor should berecorded therein. Addition of a file entry and a file identifierdescriptor with respect to the AV reservation region is not limited tothe above procedure. For example, it may be possible to divide the AVreservation region into two, and to use a region with the smaller LBNfor recording a file identifier descriptor and record a file entry fromthe leading edge of the remaining region. In this case, the upper limitof the data length recorded in the file identifier descriptor isdetermined previously, for example, by previously determining the lengthof a name of a file to be recorded, and the capacity allocation fordividing the AV reservation region is determined.

A recorded AV file is reproduced from the disk shown in FIG. 5 in thefollowing manner. First, in the same way as in Step 401 shown in FIG. 4,the content of LBN=0 to 250 on the disk 1 is read to the memory section4. Then, the recorded extent of the directory AV_DIR1 is scanned toobtain a name of a file present under the directory AV_DIR1.

Then, data in the file is accessed by the procedure described in theprior art to be reproduced. In the case where the subsequent file isreproduced continuously, the file identifier descriptors and fileentries of all the files present under the directory AV_DIR1 are read tothe memory section 4. Thus, in reproducing AV files under the directoryAV_DIR1 the extents of the files to be reproduced can be accesseddirectly, and files can be reproduced continuously at a high speedwithout seeking with respect to a file entry, as occurred according tothe conventional method.

Such continuous reproduction is realized easily by performing recordingin accordance with the processing procedure shown in FIG. 4. If therecording procedure of the present invention is not used, it is unclearin which logical block in the partition space an entry of an AV filerecorded in the directory AV_DIR1 is recorded. Similarly, the operationof reading data to the memory section 4 is realized easily at a highspeed by performing recording in accordance with the processingprocedure shown in FIG. 4. If the recording procedure of the presentinvention is not used, although it is possible to read data to thememory section 4, seeking occurs a number of times at the beginning of arecording/reproduction operation.

The recording procedure is not limited to the one shown in FIG. 4. Forexample, as described in WO 98/14938, the following may be possible: aplurality of available continuous regions are kept prior to recording ofactual data; these regions are registered in the space bitmap as “anallocated state”; and thereafter, actual data start to be recorded.

Furthermore, information on the allocation descriptor of the directoryAV_DIR1 and the space bitmap may be updated collectively after recordingof file data is completed.

Furthermore, the data structure in the partition space on a disk isinitialized as shown in FIG. 3 prior to recording of an AV file, whenrequired.

A directory/file name in which an AV file is to be recorded is notlimited to that described in Embodiment 1. Another directory/file namemay be used.

In Embodiment 1, the content of LBN=0 to 250 is read to the memorysection 4 during recording/reproduction. However, all the information isnot required to be kept in the memory section 4. Only requiredinformation may be kept during recording/reproduction, and onlyinformation that needs to be updated may be written back to the disk 1.

By keeping LBN=86 to 250 as a “not recorded” but “allocated” extent ofthe directory AV_DIR1, LBN=86 to 250 is set to be an AV reservationregion. However, the recorded position and capacity of the AVreservation region are not limited to LBN=0 to 250. Another recordedposition and capacity may be used as long as they are kept as continuousregions on the disk.

In Embodiment 1, the case using a file entry has been described.However, an extended file entry may be used. In the case of using anextended file entry, the AV reservation region may be kept as a part ofthe extent of a named data stream of the directory AV_DIR1. In thiscase, the extent forming the AV reservation region may be set to be an“allocated” and “recorded” extent.

Embodiment 2

Hereinafter, an AV data recording apparatus in Embodiment 2 of thepresent invention will be described with reference to the drawings. InEmbodiment 1, a file identifier descriptor and a file entry of an AVfile to be newly recorded are recorded in a “not recorded” but“allocated” extent of the directory AV_DIR1. In contrast, in Embodiment2, a management file to store information for managing an AV file iscreated under the directory AV_DIR1, and the management file is allowedto have a “not recorded” but “allocated” extent.

FIG. 6 illustrates a file/directory structure immediately after adirectory for recording an AV file is created in the AV data recordingapparatus in Embodiment 2 of the present invention. The file/directorystructure shown in FIG. 6 is different from the directory structureshown in FIG. 2, in that a management file (AVFILES.IFO) is presentunder the directory AV_DIR1.

FIG. 7 illustrates a data structure in a partition space when adirectory for recording an AV file is recorded. In FIG. 7, in LBN=0 to79, a space bitmap descriptor is recorded. Since LBN=251 to Last is“unallocated”, bits corresponding to the sectors therein are set at “1”.

In LBN=80, a file set descriptor is recorded. When the file entrytherein is that of the root directory, positional information isrecorded in the file set descriptor.

Furthermore, a terminating descriptor, a file entry of the rootdirectory, a directory file of the root directory, a file entry of thedirectory AV_DIR1, and a file entry of the AVFILES.IFO file are recordedin LBN=81, LBN=82, LBN=83, LBN=84, and LBN=85, respectively.

LBN=86 is an extent in which a directory file of the directory AV_DIR1is recorded. LBN=87 to 250 is an extent of the AVFILES.IFO file. Thevalue of the 2 most significant bits of an allocation descriptor is setso that the extent is “not recorded” but “allocated”. Thus, this regionbecomes an AV reservation region in Embodiment 2.

When an AV file is recorded on a disk having the above-mentioned datastructure, a processing procedure similar to that shown in FIG. 4 can beperformed. However, the processing procedure in Embodiment 2 isdifferent from that in Embodiment 1, in that the AV reservation regionfor recording a new file identifier descriptor and a file entry is a“not recorded” but “allocated” extent of AVFILES.IFO, which is amanagement file.

When an AV file is reproduced from a disk, a procedure similar to thatdescribed in Embodiment 1 can be performed. In Embodiment 2, no data isrecorded in the AVFILES. IFO file in an initial state; however, it maybe possible that attribute information and the like on the directoryAV_DIR1 are recorded in an initial state, and the AVFILES.IFO file isallowed to have an “allocated” and “recorded” extent, as well as a “notrecorded” but “allocated” extent. Furthermore, the “allocated” and“recorded” extent may be set to be an AV reservation region.

In Embodiment 2, the case using a file entry has been described.However, an extended file entry may be used. In the case of using anextended file entry, the AV reservation region may be kept as a part ofan extent of a named data stream of the file AVFILES.IFO. Furthermore,in this case, the extent forming the AV reservation region may be set tobe an “allocated” and “recorded” extent.

In Embodiment 2, the AV reservation region management file is recordedin the same directory as that for recording an AV file. However, the AVreservation region management file may be recorded in another directory.By recording the AV reservation region management file in anotherdirectory, it becomes possible to prevent the management file from beingdeleted mistakenly by a user's operation or the like.

Embodiment 3

Hereinafter, an AV data recording apparatus in Embodiment 3 of thepresent invention will be described with reference to the drawings. InEmbodiment 3, the case will be described where 100 AV files are recordedin the directory AV_DIR1. FIG. 8 illustrates a file/directory structurein Embodiment 3.

In Embodiments 1 and 2, a “not recorded” but “allocated” extent isallocated to a directory or a file, and a file entry or the like of anAV file is recorded in the extent. Embodiment 3 is different fromEmbodiments 1 and 2, in that when a directory for recording an AV fileis created, a file identifier descriptor and a file entry for an AV filealso are created in a continuous region.

FIG. 9 illustrates a data structure in a partition space in Embodiment3. In FIG. 9, each file is assigned a file name automatically, and thesefile names are recorded in the file identifier descriptor. In Embodiment3, 100 files are present under the directory AV_DIR1, so that 100 fileidentifier descriptors are recorded in the extent of the directoryAV_DIR1. An allocation descriptor in each file entry of the AV filesrecorded in LBN=101 to 200 does not refer to an extent, and the datacapacity as a file is 0.

In Embodiment 3, a file identifier descriptor and a file entry alreadyhave been recorded. Therefore, when an AV file is recorded, data areread to the memory section 4 in the same way as in the processingprocedure shown in FIG. 4. However, at Step S402, a non-recorded regionis not scanned; instead, information on file entries recorded in LBN=101to 200 is scanned, a file entry with a file capacity of 0 is detected,and data are recorded using the detected file entry as a new AV file.

When recording of data is completed, information on the position andlength of the extent recorded in the allocation descriptor of the fileentry in the memory section 4 and other file management information areupdated. Finally, the content of the memory section 4 is written back tothe disk 1 in the same way as in Step S408. Similarly, when an AV fileis reproduced, the procedure similar to that described in Embodiment 1can be performed.

In Embodiment 3, a file entry with a file capacity of 0 is detected, anddata are recorded using the detected file entry as a new AV file.However, a method for detecting a new file entry is not limited to thismethod. Another method may be used. For example, a file name in aninitial state may be changed after recording of actual AV data.Alternatively, it may be possible to determined whether or not AV datacan be recorded, using a file attribute field in a file identifierdescriptor, an extended attribute field in the file entry, and the like.

Furthermore, the data capacity of a file in an initial state is set tobe 0. However, by recording common attribute information between AVfiles and the like, data may be recorded even in an initial state.

Embodiment 4

Hereinafter, an AV data recording apparatus in Embodiment 4 of thepresent invention will be described with reference to the drawings. Asdescribed above, in Embodiments 1 to 3, file management information suchas a file entry is recorded in a region that already has been kept. InEmbodiment 4, attribute information of an AV file, as well as a fileentry are recorded in a region that has already been kept. Because ofthis, particular information on an AV file can be accessed continuouslyat a high speed.

FIG. 10 illustrates a data structure of an AV file to be recorded inEmbodiment 4. In FIG. 10, an AV file in Embodiment 4 is a transportstream based on the MPEG system, and is composed of an AV stream partthat is a video stream and an attribute information part that is aprivate stream. The AV stream part is composed of a plurality of videoobject units (hereinafter, referred to as “VOBU”).

One VOBU is AV data corresponding to 0.4 to 1 second of video data, andincludes a video data interval called a GOP (Group of Picture) under theMPEG2 standard. The GOP includes at least one I-picture, so that the GOPcan be reproduced independently. In the case of special reproductionsuch as fast-forward reproduction and fast-backward reproduction andreproduction at a specified time, an I-picture in the GOP is extractedas an image to be reproduced.

In the attribute information part, attribute information on an AV streamis recorded. For example, a recorded date and time of a file, a commentwith respect to recorded information, parameters during recording, athumbnail image, and the like are recorded. Furthermore, in theattribute information part, in addition to the above-mentioned attributeinformation, time map information is recorded for the purpose offacilitating special reproduction such as fast-forward reproduction andreproduction at a specified time with respect to an AV stream.

The time map information is the one in which a reproduction time of anAV stream is related to a recorded position, for example, as describedin JP 3028517. As shown in FIG. 11, the time map information has ahierarchical data structure composed of two tables called a time maptable and a VOBU table.

In the time map table, time maps #1, #2, . . . are arranged. Time maps#1, #2, . . . represent recorded positions of VOBU corresponding toreproduction times in the case where data is reproduced at apredetermined time interval TMU (e.g., 60 seconds) on a time axis with aleading edge of the AV stream part at a starting time.

In the VOBU table, VOBU maps, each containing a reproduction time and adata size of each VOBU, are arranged in the order of reproduction timefrom the leading edge of the AV stream part.

FIG. 12 shows the data structure of time map information in more detail.FIG. 13 shows the logical link relationship between the time map tableand the VOBU table.

Herein, time map general information includes the number of time mapsand VOBU maps included in the time map information, a time unit(hereinafter, referred to as “TMU”) representing a predetermined timeinterval in which time maps are provided, and a time offset(hereinafter, referred to as “TM_OFS”) representing a time differencebetween the leading time of the AV stream part and the time of theleading time map. The value of TM_OFS is “0”, as long as an editoperation such as deletion of the leading edge of the AV stream part isperformed.

In the time map table, a plurality of time maps #1, #2, . . . areprovided at a predetermined time interval represented by the TMU andarranged in the order of time.

Each time map is composed of a VOBU map number, a time difference(hereinafter, referred to as “TM_DIFF”), and a VOBU address(hereinafter, referred to as “VOBU_DR”). VOBU_ADR is positionalinformation in the AV stream part at the leading edge of thecorresponding VOBU.

A reproduction time (hereinafter, referred to as a “time map time”) withrespect to time map #i is represented by Formula (1).(Time map time)=(TMU*(i−1)+TM _(—) OFS)  (1)

The VOBU map number represents the number present at a reproduction timerepresented by Formula (1). For example, as shown in FIG. 13, the timemap #1 represents a time obtained by adding TM_OFS to a leading time inthe AV stream part. The time map #2 represents a time after TMU from thetime map #1. Thereafter, the time maps represent VOBU maps present atreproduction times at 2 TMU, 3TMU, . . . , respectively.

TM_DIFF represents a time difference between the leading time of thecorresponding VOBU and the time map time. Thus, the leading time of VOBU#j is represented by Formula (2).(Leading time of VOBU)=TMU*(j−1)+TM _(—) OFS _(—) TM _(—) TIFF  (2)

In the VOBU table, VOBU maps #1, #2, . . . corresponding to VOBUscontained in the AV stream part in one-to-one relationship. Each VOBUmap consists of a reference image size, a VOBU reproduction time, and aVOBU size.

The reference image size refers to the size of the first I-picture inthe VOBU, and is used for finding an image of interest for specialreproduction or reproduction at a specified time. For example, by addingsuccessively a VOBU reproduction time to the VOBU leading time until thereproduction time of an image of interest is obtained, a VOBU to bereproduced is specified and an image in the VOBU is specified.

A VOBU size is a data size of a VOBU, and is used for specifying theposition of image data of interest for special reproduction orreproduction at a specified time.

As described above, in Embodiment 4, even in the case of specialreproduction, a particular image such as an I-picture can be searchedfor at a high speed.

A file/directory structure in an initial state in Embodiment 4 is thesame as that shown in FIG. 2. FIG. 14 shows a data structure in apartition space in this case. The data structure in FIG. 14 is differentfrom that in FIG. 3, in that a region for recording a part of an AV filein addition to file management information also is kept as a “notrecorded” but “allocated” extent of the directory AV_DIR1. Therefore,the extent (2) of the directory AV_DIR1 is recorded in logical blocksLBN=86 to 500. In the case of the same number of AV files, the datastructure shown in FIG. 14 can keep more AV files, compared with thatshown in FIG. 3. In this case, the capacity to be kept equals the totalof the capacity of file management information and the capacity ofattribute information part with respect to the assumed number of AVfiles.

Regarding an AV file, an item (i.e., time map information) that isvaried depending upon the data capacity in the AV stream part isincluded in the attribute information part. However, by settingconditions such as a disk capacity, the number of AV files to berecorded, and a bit rate of an AV stream, the maximum capacity in thetime map information part to be recorded on the disk 1 can be determinedpreviously. Thus, the capacity of an AV reservation region should bekept with respect to an AV file to be recorded in the directory AV_DIR1,expecting the total capacity in the attribute information part in thecase where the capacity of the time map information part becomesmaximized.

An AV file is recorded onto a disk having the above-mentioned datastructure in accordance with a flow chart shown in FIG. 15.

In FIG. 15, first, the content of LBN=0 to 500 on the disk 1 is read tothe memory section 4 (Step S1301). Then, extent information in thedirectory AV_DIR1 in the memory section 4 is scanned to determinewhether or not there is a non-recorded region sufficient for recording afile identifier descriptor, a file entry, and an attribute informationpart of a file (Step S1302). When it is determined that there is not asufficient non-recorded region (Step S1302: No), error processing isperformed and recording of an AV file is ended. When it is determinedthat there is a sufficient non-recorded region, a file identifierdescriptor, a file entry, and an attribute information part of an AVfile are recorded in the non-recorded region in the extent of thedirectory AV_DIR1 in the memory section 4 (Step S1303).

Then, in accordance with recording of the file identifier descriptor,the file entry, and the attribute information part of an AV file, anallocation descriptor of the file entry of the directory AV_DIR1 isrewritten. More specifically, the extent length of the recorded extentis changed by addition of the file identifier descriptor, and a portionin which the file entry has been recorded is excluded from thenon-recorded extent. Furthermore, information that is determined to berecorded in the attribute information part of an AV file also isrecorded in the AV reservation region in the memory section 4.

Next, the space bitmap in the memory section 4 is scanned to determinewhether or not there are the required number of unallocated logicalblocks for recording an AV file (Step S1304). When it is determined thatthere are no the required number of unallocated logical blocks (StepS1304: No), error processing is performed, and recording of an AV fileis ended. When it is determined that there are the required number ofunallocated logical blocks, data is recorded in a logical block on arecording medium corresponding to the non-recorded region obtained inStep S1303 (Step S1305).

Furthermore, time map information is obtained at this time amongattribute information of an AV file, so that it is recordedappropriately in the AV reservation region in the memory section 4. Whenrecording of the AV fle data is completed, information on the positionand length of an extent of the AV file are recorded in an allocationdescriptor in the file entry created in Step S1303 (Step S1306).Furthermore, required information such as a file name and a filecreation time are updated with respect to the file identifier descriptorand the file entry, in addition to the allocation descriptor.

Next, with respect to the space bit map in the memory section 4, a bitcorresponding to the logical block in which data has been recorded inStep S1305 is changed to “1” representing an “allocated” state (StepS1307). Then, the content of the memory section 4 is written back toLBN=0 to 500 (Step S1308). Thus, anAV file is recorded in the directoryAV_DIR1.

In the case of recording a plurality of AV files continuously, in theflow chart in FIG. 16, Steps S1302 to S1307 are repeated after StepS1301 until recording of all the AV files is completed, and afterrecording of all the AV files is completed, a process should proceed toStep S1308. Because of this, it is not required to write a fileidentifier descriptor and a file entry onto a disk every time a file iscreated, and seeking can be reduced substantially.

FIG. 16 shows a data structure in the partition space after FILE1. DATand FILE2. DAT that are AV files are recorded in the directory AV_DIR1in accordance with the flow chart shown in FIG. 15. Herein, in the AVreservation region, a file identifier descriptor, a file entry, and anattribute information part of an AV file are recorded.

An AV file is reproduced from a disk having the data structure as shownin FIG. 16 by the procedure similar to that described in Embodiment 1.In Step S408, the content of LBN=0 to 500 on the disk 1 is read to thememory section 4.

Furthermore, in the case of reproducing a particular display time of anAV file, file identifier descriptors, file entries, and attributeinformation parts including time map information of all the AV filespresent under the directory AV_DIR1 are read to the memory section 4.Thus, an offset position in a file with respect to a certainreproduction time is obtained by processing only information in thememory section 4, and seeking is not required with respect to the disk1. As a result, special reproduction (selective reproduction ofparticular frames) can be performed easily. Furthermore, it becomespossible that various pieces of attribute information are extracted, anda list thereof is displayed to a user.

Such continuous reproduction is realized easily by performing recordingin accordance with the processing procedure shown in FIG. 15. If therecording procedure in Embodiment 4 is not used, attribute informationof an AV file is recorded in the same extent as that in the AV streampart, and distributed on the disk. As a result, seeking to extractattribute information cannot be avoided.

The positional relationship in the AV reservation region of a fileentry, attribute information, and time map information may be varied. Inthe course of reproduction of an AV file, a portion of the AVreservation region, in which attribute information of an AV file isrecorded, is read entirely to the memory section 4. However, instead ofreading the entire portion from the beginning, the attribute informationmay be read when required. In this case, compared with the prior art,seeking can be reduced, and a table for attribute information of an AVfile and a high-speed access can be read at a high speed.

Furthermore, in Embodiment 4, the AV reservation region is provided asan extent of the directory AV_DIR1. However, it may be possible tocreate a management file, and provide an AV reservation region as theextent of the management file as in Embodiment 2. In this case,recording/reproduction of an AV file is performed in the same way as inEmbodiment 2.

The AV reservation region may be kept as a plurality of extents. Forexample, it may be possible to provide an AV reservation region for afile management region as an extent of the directory AV_DIR1, and toprovide an AV reservation region for attribute information of an AV fileas an extent of the management file.

Alternatively, the following may be possible: two kinds of managementfiles are provided, an AV reservation region for a file managementregion is provided in the first management file, and an AV reservationregion for attribute information of an AV file is provided in the secondmanagement file. Furthermore, other methods may be used, as long as anAV reservation region is kept as a continuous region.

Time map information should be the one in which a reproduction time ofan AV stream is related to a recorded position, and may have a structureother than that shown in FIG. 11.

In Embodiment 4, an AV file is a transport stream based on the MPEG.However, the AV file may be in another format. Particular information ofan AV file simply may be recorded in a region that has been keptpreviously.

Embodiment 5

Hereinafter, an AV data recording apparatus in Embodiment 5 of thepresent invention will be described with reference to the drawings. Asdescribed above, in Embodiment 4, an AV file is recorded, which iscomposed of an AV stream part in which video data of MPEG2 is recordedand an attribute information part. In Embodiment 5, an AV file is anExif image file, which is composed of an Exif main image (main imagedata), and additional information related to the Exif main image.

More specifically, an AV file in Embodiment 5 is composed of a headerpart formed of additional information related to a still image and avideo data part formed of a still image data body. The additionalinformation is recorded in an AV reservation region. Because of this,particular information such as a thumbnail image of an AV file can beaccessed continuously at a high speed, by seeking only in the AVreservation region.

FIG. 17 illustrates a data structure of an AV file in the AV datarecording apparatus in Embodiment 5 of the present invention. In FIG.17, an AV file in Embodiment 5 is composed of a header part and a videodata part.

In the header part, additional information on the image data part isrecorded. For example, a recorded date and time of a file, a comment onrecorded information, parameters at a time of recording/compression, athumbnail image, and the like are recorded. Furthermore, in the videodata part, a still image data body compressed based on the JPEG systemis recorded.

A file/directory structure in the AV data recording apparatus inEmbodiment 5 is the same as that shown in FIG. 2. A data structure in apartition space thereof is the same as that shown in FIG. 14.

In the AV reservation region, file management information of an AV file,and data with a predetermined capacity from the leading edge of the AVfile are recorded. It is assumed that data with such a predeterminedcapacity include at least a thumbnail image in the header part of an AVfile.

Thus, when a thumbnail list of recorded AV files and a list of recordeddate and time are displayed to a user, information thereof is recordedin the AV reservation region that is a continuous region, so that theycan be displayed at a high speed.

A data structure of an AV file may be constructed as shown in FIG. 18:padding data are inserted into the header part so that the capacity ofthe entire header part is adjusted to be an integral multiple of thelogical block capacity of the UDF. At this time, since the capacity ofthe header part is an integral multiple of the logical block capacity ofthe UDF, the video data part always is positioned from the leading edgeof the logical block. Furthermore, only the file management informationand the header part are recorded in the AV reservation region. Thus, inthe course of recording/reproduction of an AV file, the header part canbe separated completely from the video data part, and data can beprocessed on a logical block basis; therefore, recording/reproductioncan be performed at a higher speed.

In Embodiment 5, as an AV file, an Exif file containing a main imagecompressed based on the JPEG system is used. However, the presentinvention is not limited thereto. Any still image file with a formathaving additional information in the header part may be used.

A plurality of AV directories may be present on the disk. In this case,a still image file is recorded in one directory as in Embodiment 5, anda video file of MPEG2 may be recorded in the other directory as inEmbodiment 4. Furthermore, the number of AV directories is not limitedto two. If required, the number of directories may be increased.

In this case, the AV reservation region may be managed on a directorybasis. Alternatively, it may be possible to provide a dedicatedmanagement directory and manage an AV reservation region used in eachdirectory. For example, as shown in FIG. 19, the following isconceivable: an AV reservation region management file AVFILES.IFO isplaced under a management directory AV_INFO, a still image file isrecorded in the AV directory AV_DIR1 using an AV reservation regionmanaged by the AV reservation region management file, and a video fileis recorded in the directory AV_DIR2.

A video file and a still image file are not required to be recorded inseparate directories. A video file and a still image file may be mixedin one directory.

As described above, in Embodiment 5, data recorded by a user can beseparated from information for managing the data, which prevents damageand the like to management information due to maloperation and the like.In Embodiment 5, a single AV reservation management region file is used.However, for example, an AV reservation management region file may beprovided on an AV directory basis.

Embodiment 6

Hereinafter, an AV data recording apparatus in Embodiment 6 of thepresent invention will be described with reference to the drawings. InEmbodiment 6, the case will be described where an AV directory has ahierarchical structure. It is convenient to support a hierarchicaldirectory for classifying recorded data, and the like. However, in thecase of the UDF, a directory also is handled as a kind of a file, sothat seeking cannot be avoided particularly in the case of a directorystructure with a deep hierarchy.

In Embodiment 6, a reservation region is provided for creating ahierarchical directory. FIG. 20 illustrates a file/directory structureimmediately after a directory for recording an AV file is created.

FIG. 21 shows a data structure in a partition space when thefile/directory structure shown in FIG. 20 is recorded on a disk used inthe AV data recording apparatus in Embodiment 6 of the presentinvention.

LBN=86 to 250 is an extent (2) of the AV_DIR1 directory, and the valueof the 2 most significant bits of an allocation descriptor is set sothat the extent (2) is “not recorded” but “allocated”. Hereinafter, theextent (2) will be referred to as an AV directory reservation region.

A subdirectory is created under the AV directory on the disk having theabove-mentioned structure in accordance with a flow chart shown in FIG.22.

First, the content of LBN=0 to 250 on the disk 1 is read to the memorysection 4 (Step S171). Then, information in the AV directory reservationregion in the memory section 4 is scanned to determine whether or notthere is a non-recorded region sufficient for newly recording a fileidentifier descriptor and a file entry for the AV subdirectory (StepS172). When it is determined that there is not a sufficient non-recordedregion (Step S172: No), error processing is performed, and creation ofan AV subdirectory is ended.

When it is determined that there is a sufficient non-recorded region, afile identifier descriptor and a file entry are recorded in thenon-recorded region in the AV reservation region in the memory section 4(Step S173). At this time, the size of the extent of the AV_DIR1directory is changed due to recording of the file identifier descriptorand the file entry; therefore, an allocation descriptor of the fileentry of the AV_DIR1 directory is rewritten in accordance with thechange.

More specifically, the extent length of the extent (1) is changed byaddition of the file identifier descriptor, and a portion in which thefile entry has been recorded is excluded from the extent (2).

Next, the space bitmap in the memory section 4 is scanned to determinewhether or not there are the required number of continuous unallocatedlogical blocks for recording an AV subdirectory and an AV reservationregion to be allocated thereto (Step S174). When it is determined thatthere are not the required number of continuous unallocated logicalblocks (Step S174: No), processing is ended.

When it is determined that there are the required number of continuousunallocated logical blocks, data are recorded in a logical block on thedisk corresponding to an unallocated region obtained in Step S173 (StepS175). Herein, recording of data includes creation of a directory fileof an AV subdirectory, and keeping of an AV reservation region allocatedto the AV subdirectory.

When recording of data is completed, in order to update file managementinformation of the AV subdirectory file, information on the position andlength of the extent of the AV subdirectory file is recorded in anallocation descriptor of the file entry in the memory section 4 createdin Step S173 (Step S176).

Furthermore, required information such as a file name and a filecreation time also are updated with respect to the file identifierdescriptor and the file entry, in addition to the allocation descriptor.

Next, with respect to the space bitmap in the memory section 4, bitscorresponding to logical blocks in which data is recorded in Step S173are changed to “1” representing an “allocated” state (Step S177).

Then, the content of the memory section 4 is written back to LBN=0 to250 (Step S178). Thus, an AV subdirectory AV_SUB_DIR1 is created underthe directory AV_DIR1 by a series of processing. FIG. 23 shows adirectory structure in this case. FIG. 24 shows a data structure in thepartition space in this case.

Herein, in the same way as in Embodiment 1, new file entries arerecorded in logical blocks in the decreasing order of LBN in the AVdirectory reservation region. On the other hand, the file identifierdescriptor is added to the end of the extent (1) that is a recordedextent of the directory AV_DIR1. Herein, an AV file is not recorded, anda directory file is recorded.

The created AV subdirectory is an extent (2), and the value of the 2most significant bits of an allocation descriptor is set so that theextent (2) is “not recorded” but “allocated”. When an AV file isrecorded in the directory AV_SUB_DIR1 hereinafter, it is recorded in thesame procedure as that in Embodiment 1, using the AV reservation region.

Furthermore, an AV file is recorded on the disk having theabove-mentioned data structure in accordance with a flow chart in FIG.25.

First, the contents of LBN=0 to 79 and LBN=250 to 400 on the disk 1 areread to the memory section 4 (Step S201). Then, information in the AVreservation region in the subdirectory AV_SUB_DIR1 in the memory section4 is scanned to determine whether or not there is a non-recorded regionsufficient for newly recording a file identifier descriptor and a fileentry (Step S202). When it is determined that there is not a sufficientnon-recorded region (Step S202: No), error processing is performed, andrecording of an AV file is ended.

When it is determined that there is a sufficient non-recorded region, afile identifier descriptor and a file entry are recorded in anon-recorded region in the AV reservation region in the subdirectoryAV_SUB_DIR1 in the memory section 4 (Step S203).

Then, the space bitmap in the memory section 4 is scanned to determinewhether or not there are the required number of unallocated logicalblocks for recording AV files (Step S204). When it is determined thatthere are not the required number of unallocated logical blocks (StepS204: No), error processing is performed, and recording is completed.

When it is determined that there are the required number of unallocatedlogical blocks, data is recorded in a logical block on a recordingmedium corresponding to the non-recorded region obtained in Step S203(Step S205).

When recording of AV file data is completed, in order to update the filemanagement information of the AV file, information on the position andlength of the extent of the AV file is recorded in an allocationdescriptor of the file entry in the memory section 4 created in StepS205 (Step S206).

Next, with respect to the space bitmap in the memory section 4, bitscorresponding to logical blocks in which data are recorded in Step S205are changed to “1” representing an “allocated” state (Step S207).

Then, the content of the memory section 4 is written back to LBN=0 to 79and LBN=250 to 400 on the disk 1 (Step S208). Thus, an AV file can berecorded in the directory AV_SUB_DIR1.

FIG. 26 shows a data structure in a partition space after FILE 1.DAT andFILE2.DAT that are AV files are recorded in the directory AV SUB_DIR1 byprocessing shown in FIG. 25.

In FIG. 26, in the AV reservation region allocated to the directoryAV_SUB_DIR1, logical blocks are used in the decreasing order of LBN forrecording new file entries. On the other hand, a file identifierdescriptor is added to the end of the extent (1) that is a recordedextent of the directory AV_SUB_DIR1. In the case where a predeterminednumber of AV files are recorded in the directory AV_SUB_DIR1, anothersubdirectory is created under the directory AV_DIR1, and an AV file isrecorded in this directory.

An AV file is reproduced from a disk having the data structure shown inFIG. 26 by the following procedure. First, a root directory is read, andthe directory AV_DIR1 and the directory AV_SUB_DIR1 are read. At thistime, a portion corresponding to the AV reservation region allocated tothe directory AV_SUB_DIR1 (i.e., LBN=251 to 400) is read to the memorysection 4.

Then, the recorded extent of the directory AV_SUB_DIR1 is scanned toobtain a name of a file in the directory AV_SUB_DIR1.

Next, data in the file is accessed and reproduced in the proceduredescribed in the prior art.

In the case where a file in another AV subdirectory is read, an AVreservation region allocated to the AV subdirectory is read, andthereafter, a file is accessed.

As described above, in Embodiment 6, even in the case where a directoryhas a hierarchical structure, seeking at a time of creating a file andreading a file can be reduced substantially.

A new AV subdirectory should be created, for example, in the case of auser's instruction, or in the case where a predetermined number of filesare recorded in the AV subdirectory.

Embodiment 7

Hereinafter, an AV data recording apparatus in Embodiment 7 of thepresent invention will be described with reference to the drawings. InEmbodiment 7, the case will be described where an AV reservation regionalso is allocated to an AV subdirectory when the AV directory has ahierarchical structure.

First, in Embodiment 7, a file/directory structure immediately after adirectory for recording an AV directory is created is the same as thatshown in FIG. 20. Furthermore, a data structure in a partition space isthe same as that shown in FIG. 21. FIG. 27 is a flow chart showingprocessing in the case where a subdirectory is created under an AVdirectory on a disk having the above-mentioned data structure.

In FIG. 27, the content of LBN=0 to 250 on the disk 1 is read to thememory section 4 (Step S241). Then, information in an AV directoryreservation region in the memory section 4 is scanned to determinewhether or not there is a non-recorded region sufficient for newlyrecording a file identifier descriptor and a file entry for an AVsubdirectory (Step S242).

When it is determined that there is not a sufficient non-recorded region(Step S242: No), error processing is performed, and creation of an AVsubdirectory is ended. When it is determined that there is a sufficientnon-recorded region (Step S242: Yes), a file identifier descriptor, afile entry, and an AV subdirectory file are recorded in a non-recordedregion in the AV reservation region in the memory section 4 (Step S243).

When a file identifier descriptor, a file entry, and an AV subdirectoryfile are recorded, the size of the extent of the AV_DIR1 directory ischanged. Therefore, an allocation descriptor of the file entry of theAV_DIR1 directory is rewritten in accordance with the change. Morespecifically, the extent length of the extent (1) is changed by additionof the file identifier descriptor, and a portion in which the file entryand the directory file are recorded is excluded from the extent (2).

Next, information on a space bitmap in the memory section 4 is updatedif required (Step S244). The content of the memory section 4 is writtenback to LBN=0 to 250 on the disk 1 (Step S245).

An AV subdirectory AV_SUB_DIR1 is created under the directory AV_DIR1 bythe above-mentioned series of processing. A directory structure aftercreation of an AV subdirectory is the same as that shown in FIG. 23.

FIG. 28 shows a partition structure after creation of an AVsubdirectory. In FIG. 28, in the same way as in Embodiment 1, a fileidentifier descriptor is recorded so as to be added to the end of theextent (1) that is a recorded extent of the subdirectory AV_SUB_DIR1. Onthe other hand, for recording a new file entry and a directory file,logical blocks are used in decreasing order of LBN in the AV directoryreservation region.

Next, FIG. 29 is a flow chart showing processing for recording an AVfile on a disk having the above-mentioned data structure. In FIG. 29,the content of LBN=0 to 250 on the disk 1 is read to the memory section4 (Step S261), and information in an AV directory reservation region inthe memory section 4 is scanned to determine whether or not there is anon-recorded region sufficient for newly recording a file identifierdescriptor and a file entry (Step S262).

When it is determined that there is not a sufficient non-recorded region(Step S262: No), error processing is performed, and recording of an AVfile is ended. When it is determined that there is a sufficientnon-recorded region (Step S262: Yes), a file identifier descriptor and afile entry are recorded in a non-recorded region in the AV reservationregion in the memory section 4 (Step S263).

Next, the space bitmap in the memory section 4 is scanned to determinewhether or not there are the required number of unallocated logicalblocks for recording an AV file (Step S264). VVhen it is determined thatthere are not the required number of unallocated logical blocks (StepS264: No), error processing is performed, and recording of an AV file isended. When it is determined that there are the required number ofunallocated logical blocks (Step S264: Yes), data are recorded in alogical block corresponding to the region (Step S265).

When recording of AV file data is completed, in order to update filemanagement information of the AV file, information on the position andlength of the extent of the AV file is recorded in an allocationdescriptor of the file entry in the memory section 4 created in StepS263 (Step S266).

Next, with respect to the space bitmap in the memory section 4, bitscorresponding to logical blocks in which data is recorded in Step S266are changed to “1” representing an “allocated” state (Step S267). Then,the content of the memory section 4 is written back to LBN=0 to 250 onthe disk 1 (Step S268). Thus, an AV file can be recorded in thesubdirectory AV_SUB_DIR1.

FIG. 30 shows a structure in a partition space after an AV fileFAILE1.DAT is recorded in the AV subdirectory AV_SUB_DIR1, and a newsubdirectory AV_SUB_DIR2 is created. In FIG. 30, in an AV reservationregion in the directory AV_DIR1, an AV subdirectory, file managementinformation of an AV file recorded in the AV subdirectory, and an AVsubdirectory file are recorded. Because of this structure, even in thecase where files in different AV subdirectories are accessedcontinuously, seeking with respect to the disk can be reduced. FIG. 31shows a directory structure in this case.

When an AV file is reproduced from a disk having the above-mentioneddata structure, a root directory is read, and a directory AV_DIR1 isread. At this time, a region containing a portion corresponding to an AVreservation region allocated to the directory AV_DIR1 (i.e., LBN=0 to250) is read to the memory section 4.

Then, an extent of the subdirectory AV_SUB_DIR1 in the memory section 1is scanned to obtain a name of a file recorded in the subdirectory AVSUB_DIR1.

Even in the case where a file in another AV subdirectory is read, sincethe extent of the directory file has already been read to the memorysection 4, an intended file can be accessed by scanning suchinformation.

As described above, in Embodiment 7, even in the case where a directoryhas a hierarchical structure, seeking during creation/reading of a filecan be reduced substantially.

Embodiment 8

For the purpose of performing real-time recording, an AV file is oftenrecorded, skipping a defective block without conducting replacementprocessing, as described in WO 98/14938.

On the other hand, when file management information recorded in an AVreservation region cannot be read due to a defect of a disk or the like,reproduction of a file becomes impossible; therefore, recording withhigh reliability is required.

According to an AV data recording method in Embodiment 8, when adirectory for recording an AV file is created, and an AV reservationregion is kept, a defective block is examined. When a defective block isfound, the subsequent block is used instead of the defective block, andan AV reservation region is kept.

Because of the above, continuity of data to be recorded in the AVreservation region is not impaired, and recording can be performed withhigh reliability.

Embodiment 9

In the case where an AV file has a thumbnail image as a separate file, acontinuous region for recording the thumbnail image is kept as areservation region.

Since the thumbnail image is recorded in the continuous region, athumbnail list of a recorded file can be displayed to a user at a highspeed.

Embodiment 10

In the above-mentioned embodiments, when a new AV file is recorded, itis determined whether or not there is a non-recorded region in an AVreservation region; when it is determined that there is not a sufficientnon-recorded region for recording a new AV file, error processing isperformed, and recording of an AV file is ended.

However, according to the above-mentioned processing, even when a diskcapacity remains, if a non-recorded region is used up in an AVreservation region, an AV file cannot be recorded therein any more.

In Embodiment 10, in the case where an AV reservation region has aninsufficient capacity, a new AV reservation region is kept, andthereafter, an AV file is recorded.

FIG. 32 shows a partition space when there is no non-recorded region inan AV reservation region due to recording of an AV file. In this case, aplurality of AV files are recorded in LBN=251 to 685. In LBN=86 to 250that is an AV reservation region, file management information and thelike of file entries with respect to the AV files are recorded. Thus,even if it is attempted to record a new AV file, the AV reservationregion has no non-recorded region, so that an AV file cannot berecorded.

A new AV reservation region is kept as a “not recorded” but “allocated”extent of the directory AV_DIR1. Processing for keeping a new AVreservation region is performed in the procedure shown in FIG. 33.

In FIG. 33, first, information on the space bitmap is scanned todetermine whether or not there are the required number of continuousunallocated logical blocks for keeping a new AV reservation region (StepS331). When it is determined that there are not the required number oflogical blocks (Step S331: No), error processing is performed, and anoperation of keeping an AV reservation region is ended (Step S332).

When it is determined that there are the required number of logicalblocks (Step S331: Yes), the unallocated region is kept as a “notrecorded” but “allocated” extent (3) of the directory AV_DIR1. Morespecifically, information on the position and length of the extent (3)is recorded in an allocation descriptor in the file entry of thedirectory AV_DIR1 (Step S333).

Next, with respect to the space bitmap in the memory section 4, bitscorresponding to logical blocks of the extent (3) are changed to “1”representing an “allocated” state (Step S334).

FIG. 34 shows a state of a partition space after a new AV reservationregion is kept. In FIG. 34, LBN=686 to 850 is kept as a new AVreservation region.

The processing procedure for keeping a new AV reservation region is notlimited to the above-mentioned order. For example, the following may bepossible: after it is determined whether or not there are the requirednumber of logical blocks, information on the space bitmap is changed;thereafter, information on the extent (3) is recorded in an allocationdescriptor in the file entry of the directory AV_DIR1.

Furthermore, as described in Embodiment 2, in the case where the AVreservation region is kept as an extent of a management fileAVFILES.IFO, a new AV reservation region should be kept as an extent ofthe management file AVFILES.IFO.

Furthermore, in the case where an AV reservation region is kept as anamed stream, the new AV reservation region may be kept as a namedstream.

As described above, in the AV data recording apparatus of the presentinvention, by recording file management information and attributeinformation of an AV file in a continuous region that has been keptpreviously, seeking with respect to a disk, which prevents real-timerecording/reproduction of an AV file, can be reduced.

Furthermore, even in the case where a large number of still images ofJPEG compression are recorded, since the file management region isrecorded in a continuous region, the still images can be read at a highspeed.

The invention may be embodied in other forms without departing from thespirit or essential characteristics thereof. The embodiments disclosedin this application are to be considered in all respects as illustrativeand not limiting. The scope of the invention is indicated by theappended claims rather than by the foregoing description, and allchanges which come within the meaning and range of equivalency of theclaims are intended to be embraced therein.

1. An AV data recording apparatus, comprising: a recording/reproducingsection for recording AV data onto a disk and reproducing the recordedAV data; and a system control section for controlling a method ofrecording/reproducing AV data, wherein the apparatus has extentmanagement information for managing continuous blocks on the disk as anextent, the apparatus has file management information for managing agroup of the extents as a file, the apparatus has directory informationfor managing a group of the files as a directory, an area in a user areais kept as a reservation extent for recording at least any one of thedirectory information, the file management information, a part of thefile, and a whole of the file, and information concerning the positionand capacity of the reservation extent is recorded previously on thedisk, the information concerning the reservation extent being differentfrom said any one of the director information, the file managementinformation, the part of the file or the whole of the file.
 2. An AVdata recording apparatus according to claim 1, wherein the reservationextent is kept as an allocated extent.
 3. An AV data recording method,comprising: recording AV data onto a disk and reproducing the recordedAV data; controlling a method of recording/reproducing AV data; usingextent management information for managing continuous blocks on the diskas an extent, using file management information for managing a group ofextents as a file, using directory information for managing a group ofthe files as a directory, keeping an area in a user area a reservationextent for recording at least any one of the directory information, thefile management information, a part of the file, and a whole of thefile, and recording previously on the disk information concerning theposition and capacity of the reservation extent, the informationconcerning the reservation extent being different from said any one ofthe directory information, the file management information, the part ofthe file or the whole of the file.
 4. An AV data recording methodaccording to claim 3, wherein the reservation extent is kept as anallocated extent.
 5. An AV data recording apparatus according to claim2, wherein the reservation extent is kept as an allocated and recordedextent.
 6. An AV data recording method according to claim 4, wherein thereservation extent is kept as an allocated and recorded extent.